Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In Django 1.8
CurrentSiteManager
has the newuse_in_migrations
flag set toTrue
. The purpose of the flag is so the correct default manager can be used in RunPython operations, etc.This means
makemigrations
generates a migration to explicitly set the manager on every model that uses it. The alternative is just to turn it off, which is what I've done in the first commit here.I've also added a migration for Django 1.8's longer emailfield. Should that be wrapped in a version check?